Thermal management of integrated circuits

ABSTRACT

A system includes a programmable logic device (PLD) and a processor. The processor determines sets of power values associated with respective portions of a plurality of portions of the PLD. The processor also determines a temperature value for each portion of the plurality of portions based on the sets of power values and platform data associated with the PLD. Additionally, the processor generates a power map indicative of an expected amount of power for each portion of the plurality of portions based on the sets of power values. Furthermore, the processor generates a heat map indicative of an expected temperature value for each portion of the plurality of portions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/870,442, filed Jan. 12, 2018, entitled “THERMAL MANAGEMENT OFINTEGRATED CIRCUITS,” which is hereby incorporated by reference in itsentirety for all purposes.

BACKGROUND

The present disclosure relates generally to managing integrated circuitsto prevent overheating. More specifically, the present disclosurerelates to systems and methods for actively monitoring temperature andpower of an integrated circuit and controlling operations of theintegrated circuit based on the monitored temperature and power.

This section is intended to introduce the reader to various aspects ofart that may be related to various aspects of the present disclosure,which are described and/or claimed below. This discussion is believed tobe helpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

Programmable logic devices are a class of integrated circuits that canbe programmed to perform a wide variety of operations. When thetemperature of a programmable logic device exceeds an operatingtemperature of the programmable logic device, overheating occurs. Aswith other electronic devices, overheating may decrease the performanceof a programmable logic device, and, in some cases, may damage theprogrammable logic device or its components.

In some cases, a temperature sensor may be used to detect temperatureassociated with the programmable logic device. However, temperaturesensors generally detect a temperature associated with a specific areaof the programmable logic device. Temperatures associated with otherareas of the programmable logic device may differ from that of thetemperature of the area served by the temperature sensor, making itdifficult to identify overheating in those other areas of theprogrammable logic device.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages of the disclosure may become apparent upon reading thefollowing detailed description and upon reference to the drawings inwhich:

FIG. 1 is a block diagram of a system that may generate a power map anda heat map of an integrated circuit and control the integrated circuitusing the power and heat map, in accordance with an embodiment of thepresent disclosure;

FIG. 2 is a block diagram of an integrated circuit that includesmultiple sectors of programmable logic, in accordance with an embodimentof the present disclosure;

FIG. 3 is a block diagram of a system that may refine power maps andheat maps of an integrated circuit, in accordance with an embodiment ofthe present disclosure;

FIG. 4 is a flow chart of a process of controlling an integrated circuitbased on the power maps and the heat maps, in accordance with anembodiment of the present disclosure;

FIG. 5 is a flow chart of a process for generating a power map and aheat map of an integrated circuit, in accordance with an embodiment ofthe present disclosure;

FIG. 6 is a schematic diagram of a portion of an integrated circuit, inaccordance with an embodiment of the present disclosure;

FIG. 7 is a portion of an integrated circuit that includes power valuesassociated with channels and of transceiver blocks of an integratedcircuit, in accordance with an embodiment of the present disclosure;

FIG. 8 is a graph showing static power of an integrated circuit as afunction of junction temperature, in accordance with an embodiment ofthe present disclosure;

FIG. 9 is a diagram of a power map and its relationship to an integratedcircuit, in accordance with an embodiment of the present disclosure;

FIG. 10 is diagrams of several embodiments of an integrated circuit, inaccordance with embodiments of the present disclosure;

FIG. 11 is a diagram of a power map and its relationship to anintegrated circuit, in accordance with an embodiment of the presentdisclosure;

FIG. 12 is diagrams of power maps and heat maps associated with variousoperating scenarios of an integrated circuit, in accordance with anembodiment of the present disclosure;

FIG. 13 is a flow chart of a process of refining power maps and heatmaps, in accordance with an embodiment of the present disclosure; and

FIG. 14 is a flow chart of a process for controlling operation of anintegrated circuit, in accordance with an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

One or more specific embodiments of the present disclosure will bedescribed below. In an effort to provide a concise description of theseembodiments, not all features of an actual implementation are describedin the specification. It should be appreciated that in the developmentof any such actual implementation, as in any engineering or designproject, numerous implementation-specific decisions must be made toachieve the developers' specific goals, such as compliance withsystem-related and business-related constraints, which may vary from oneimplementation to another. Moreover, it should be appreciated that sucha development effort might be complex and time consuming, but wouldnevertheless be a routine undertaking of design, fabrication, andmanufacture for those of ordinary skill having the benefit of thisdisclosure.

When introducing elements of various embodiments of the presentdisclosure, the articles “a,” “an,” and “the” are intended to mean thatthere are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.Additionally, references to “one embodiment” or “an embodiment” of thepresent disclosure are not intended to be interpreted as excluding theexistence of additional embodiments that also incorporate the recitedfeatures. Furthermore, the phrase A “based on” B is intended to meanthat A is at least partially based on B. Moreover, unless expresslystated otherwise, the term “or” is intended to be inclusive (e.g.,logical OR) and not exclusive (e.g., logical XOR). In other words, thephrase A “or” B is intended to mean A, B, or both A and B.

This disclosure generally relates to controlling operations ofintegrated circuits. More specifically, power maps and heat maps ofintegrated circuits may be generated and refined (i.e., updated), suchthat they are utilized to control the operation of the integratedcircuits. Undesired power levels or temperatures may cause overheating,which can compromise performance of integrated circuits or damageintegrated circuits or components thereof. For example, certain levelsof power or overheating may cause configuration random access memorythat stores values of a programmable logic device fabric to storeincorrect values or lose stored values, which can affect operation ofthe integrated circuit.

With the foregoing in mind, in some embodiments, a controller or othersuitable device may receive temperature data via temperature sensorsdisposed on certain portions of the integrated circuit. In addition, thecontroller may receive power data from accelerator functional units(AFUs), voltage regulators, and the like of the integrated circuit.Based on the data acquired by these components and other knowninformation (e.g., transceiver configuration, incidence coefficientmatrix, AFU slot size and population), the controller may determine thetemperature and power of different portions of the integrated circuitmore accurately. In one embodiment, the controller may use thedetermined temperature and power properties of various portions of theintegrated circuit to generate heat and power maps associated with theintegrated circuit.

To detect portions of integrated circuits that are utilizing anundesirable amount of power and/or operating at an undesirabletemperature, the controller may consult the heat and power maps of theintegrated circuit to manage operations of the integrated circuit. Thatis, by utilizing the heat and power maps, the controller may adjustoperations of the integrated circuit to reduce or prevent the integratedcircuit from drawing an excessive amount of electrical power and fromoverheating in any particular region.

With the foregoing in mind, FIG. 1 illustrates a block diagram of asystem 10 that may generate a power map and a heat map of an integratedcircuit 12. The designer may specify a program or circuit design to beimplemented, such as an OpenCL program, which may enable the designer tomore efficiently and easily provide programming instructions toimplement a set of programmable logic for the integrated circuit 12without requiring specific knowledge of certain computer programminglanguages (e.g., Verilog or VHDL).

In certain embodiments, designers may implement their circuit designsusing design software 14, such as a version of Quartus by IntelCorporation™. The design software 14 may use a compiler 16 to convertthe program into a machine-readable instructions representative of theprogram provided to the design software 14 to a host 18 and theintegrated circuit 12. For example, the integrated circuit 12 mayreceive one or more kernel programs (bitstreams) 20, which describe thehardware implementations that should be stored in the integrated circuit12. The host 18 may receive a host program 22 which may be implementedby the kernel programs (bitstreams) 20. To implement the host program22, the host 18 may communicate instructions from the host program 22 tothe integrated circuit 12 via a communications link 24, which may be,for example, direct memory access (DMA) communications or peripheralcomponent interconnect express (PCIe) communications. In someembodiments, the kernel programs (bitstreams) 20 and the host 18 mayenable configuration and/or partial reconfiguration of a partition 26 onthe integrated circuit 12. The partition 26 may be a region on theintegrated circuit 12 with adaptable logic that may facilitateconfiguration and/or partial reconfiguration of the integrated circuit12, such that certain functionalities may be added, removed, and/orswapped before and/or during the runtime of the integrated circuit 12.For example, the integrated circuit 12 may be a programmable logicdevice (PLD), and the partition 26 may be a region of the integratedcircuit 12 that can be configured by an end-user of the integratedcircuit 12.

The design software 14 may also be used by the designers to generatepower maps 28 and heat maps 30 of the integrated circuit 12. Morespecifically, a processor 32 that may process (e.g., send to compiler16) the design software 14 may generate the power maps 28 and heat maps30 based on the hardware implementations of the integrated circuit 12 asspecified in the design software 14. For instance, the power maps 28 andheat maps 30 may respectively pertain to expected power consumption andexpected temperatures of portions of the integrated circuit 12, and theexpected power consumption and temperatures may be determined based on ahardware implementation to be employed by the integrated circuit 12. Forexample, the power maps 28 and heat maps 30 may respectively provideestimations of power and temperature values associated with each sectorof a sectorized FPGA or for virtual regions of the integrated circuit12, such as portions of the partition 26 that may be defined by anend-user. Additionally, the host 18 may receive power maps 28 and heatmaps 30 that the processor 32 generates.

The integrated circuit 12 may be a programmable logic device, such as afield programmable gate array (FPGA) 40, as shown in FIG. 2 . For thepurposes of this example, the FPGA 40 is referred to as an FPGA, thoughit should be understood that the device may be any suitable type ofprogrammable logic device (e.g., an application-specific integratedcircuit and/or application-specific standard product). In one example,the FPGA 40 is a sectorized FPGA of the type described in U.S. patentapplication Ser. No. 14/460,548, “Programmable Circuit Having MultipleSectors.”

In the example of FIG. 2 , the FPGA 40 may include transceiver circuitry44 for driving signals off of the FPGA 40 and for receiving signals fromother devices. Interconnection resources 46 may be used to routesignals, such as clock or data signals, through the FPGA 40. The FPGA 40of FIG. 2 is sectorized, meaning that programmable logic resources maybe distributed through a number of discrete programmable logic sectors48. Each programmable logic sector 48 may include a number ofprogrammable logic elements 50 having operations defined byconfiguration memory 52 (e.g., configuration random access memory(CRAM)). The programmable logic elements 50 may include combinational orsequential logic circuitry. For example, the programmable logic elements50 may include look-up tables, registers, multiplexers, routing wires,and so forth. A designer may program the programmable logic elements 50to perform a variety of desired functions. A power supply 54 may providea source of voltage and current to a power distribution network (PDN) 56that distributes electrical power to the various components of the FPGA40. In some embodiments, different voltages or currents may be suppliedto different sectors 48 or regions (e.g., groups of one or more sectors48) of the FPGA 40. Operating the circuitry of the FPGA 40 causes powerto be drawn from the power distribution network 56.

There may be any suitable number of programmable logic sectors 48 on theFPGA 40. Indeed, while 29 programmable logic sectors 48 are shown here,it should be appreciated that more or fewer may appear in an actualimplementation (e.g., in some cases, on the order of 50 to 100 sectorsor more). Each programmable logic sector 48 may include a sectorcontroller (SC) 58 that controls the operation of the programmable logicsector 48. Each sector controller 58 may be in communication with adevice controller (DC) 60. Each sector controller 58 may accept commandsand data from the device controller 60, and may read data from and writedata into its configuration memory 52 based on control signals from thedevice controller 60. In addition to these operations, the sectorcontroller 58 may be augmented with numerous additional capabilities.

The sector controllers 58 and the device controller 60 may beimplemented as state machines and/or processors. For example, eachoperation of the sector controllers 58 or the device controller 60 maybe implemented as a separate routine in a memory that includes a controlprogram. This control program memory may be fixed in a read-only memory(ROM) or stored in a writable memory, such as random-access memory(RAM). The ROM may have a size larger than would be used to store onlyone copy of each routine. This may allow each routine to have multiplevariants depending on “modes” the local controller may be placed into.When the control program memory is implemented as RAM, the RAM may bewritten with new routines to implement new operations and functionalityinto the programmable logic sectors 48. This may provide usableextensibility in an efficient and easily understood way. This may beuseful because new commands could bring about large amounts of localactivity within the sector at the expense of only a small amount ofcommunication between the device controller 60 and the sectorcontrollers 58.

Each sector controller 58 thus may communicate with the devicecontroller 60, which may coordinate the operations of the sectorcontrollers 58 and convey commands initiated from outside the FPGAdevice 40, such as commands initiated by the processor 32. To supportthis communication, the interconnection resources 46 may act as anetwork between the device controller 60 and each sector controller 58.The interconnection resources 46 may support a wide variety of signalsbetween the device controller 60 and each sector controller 58. Forexample, these signals may be transmitted as communication packets.

The FPGA 40 may be electrically programmed. With electrical programmingarrangements, the programmable logic elements 50 may include one or morelogic elements (wires, gates, registers, etc.). For example, duringprogramming, configuration data may be loaded into the configurationmemory 52 using input/output pins and input/output circuitry. In oneexample, the configuration memory 52 may be implemented as configurationrandom-access-memory (CRAM) cells. The use of configuration memory 52based on RAM technology is described herein is intended to be only oneexample. Moreover, configuration memory 52 may be distributed (e.g., asRAM cells) throughout the various programmable logic sectors 48 the FPGA40. The configuration memory 52 may provide a corresponding staticcontrol output signal that controls the state of an associatedprogrammable logic element 50 or programmable component of theinterconnection resources 46. The output signals of the configurationmemory 52 may be applied to the gates of metal-oxide-semiconductor (MOS)transistors that control the states of the programmable logic elements50 or programmable components of the interconnection resources 46.

As discussed above, the integrated circuit 12 may receive one or morekernel programs (bitstreams) 20 that are implemented onto the integratedcircuit 12. Keeping this in mind, FIG. 3 is a block diagram of a system70 that may be used to refine power maps 28 and heat maps 30 as well ascontrol the integrated circuit using the power maps 28 and heat maps 30.The regions may correspond to the kernel programs (bitstreams) 20. Forexample, the integrated circuit 12 (e.g., FPGA 40) may include a staticregion 72 and several partial reconfiguration regions 74. While theillustrated embodiment shows a single static region 72 and two partialreconfiguration regions 74, it should be noted the integrated circuit 12may include any suitable number of static regions 72 and partialreconfiguration regions 74. The regions (e.g., static region 72 andpartial configuration regions 74) of the integrated circuit 12 may beprogrammed and/or designed by various parties. For example, the regionsmay be programmed and/or designed by the maker of the integrated circuit12, the user (i.e., user-defined), a third-party, or a combinationthereof. The static region 72 corresponds to area on the integratedcircuit 12 that is typically not configured to be reconfigured (i.e.,reprogrammed). The partial reconfiguration regions 74 correspond toareas on the integrated circuit 12 that can be modified (i.e., partiallyreconfigured) to implement new logic.

The various regions of the integrated circuit 12 may correspond todifferent functions associated with the integrated circuit 12. Forexample, in the illustrated embodiment, the static region 72 isassociated with control functions associated with the integrated circuit12. For instance, the static region 72 may interface with anotherprocessor 76 that controls the integrated circuit 12 and/or otherintegrated circuits. It should be noted that the processor 76 differsfrom the processor 32 of FIG. 1 in that while the processor 32 mayexecute the design software 14 and generate the power map 28 and heatmap 30, the processor 76 may control operation of the FPGA 40 after akernel program (bitstream) 20 has been implemented on the FPGA 40. Asdiscussed below, the processor 76 may also update the power map 28 andheat map 30. Additionally, in the illustrated embodiment, the partialreconfiguration regions 74 correspond to accelerator functional units(AFUs), which may be utilized to perform designated functions. Forexample, each of the partial reconfiguration regions 74 may performcertain calculations that are defined by a user via the design software14.

As additionally illustrated, the processor 76 is communicatively coupledto memory 80 that includes thermal management instructions 78 that areexecutable by the processor 76. The thermal management instructions 78may include power maps 28 and heat maps 30 of the integrated circuit 12(e.g., power and heat maps 28 and 30 generated via execution of thedesign software 14) as well as instructions regarding how the processor76 should manage the integrated circuit 12 based on the power and heatmaps 28 and 30. For instance, based on the thermal managementinstructions 78, the processor 76 may determine which partialreconfiguration region 74 should be allocated to perform a calculation.Additionally, the processor 76 may refine (e.g., update, modify) powermaps 28 and heat maps 30 over time. For instance, a power map 28 and aheat map 30 may be generated before the FPGA 40 implements the kernelprograms (bitstreams) 20 stored on the memory 80 (e.g., within thethermal management instructions 78), and the processor 76 may alter thepower and heat maps 28 and 30 based on the FPGA 40 after a hardwareconfiguration has been implemented onto the FPGA 40. Generation andrefinement of the heat maps 28 and power maps 30 are discussed ingreater detail below.

With the foregoing in mind, FIG. 4 is a flow chart of a process 100 forcontrolling an integrated circuit (e.g., integrated circuit 12 of FIG. 1or FPGA 40 of FIG. 2 ). The process 100 may be performed by acombination of the processors 32 and 76 by respectively executing thedesign software 14 and the thermal management instructions 78.Additionally, before proceeding to discuss the process 100 in greaterdepth, it should be noted that the process 100 provides a generaltechnique that is elaborated upon below in FIGS. 5-12 . That is, FIG. 4and the process 100 are intended to provide an overview of features ofthe present disclosure, and more detail regarding elements of theprocess 100 is provided following the discussion of the process 100.

At block 102, the processor 32 generates a power map 28 of the FPGA 40.In one embodiment, the power map 28 is generated based oncharacteristics of the FPGA 40 as well as other factors, such ascharacteristics of a system in which the FPGA 40 is included.Additionally, the power map 28 may be specific to each sector 48 of theFPGA 40. Moreover, the power map 28 may be generated before at least aportion of the kernel program (bitstream) 20 is implemented on the FPGA40. Additional details with regard to generating the power map 28 willbe described below with reference to FIG. 5 .

At block 104, the processor 32 generates a heat map 30. The heat map 30may provide an expected temperature for each sector 48 of the FPGA 40,and the heat map 30 may be generated based at least partially on thepower map 28 generated at block 102. As with the power map 28, the heatmap 30 may be generated before at least a portion of the kernel program(bitstream) 20 is implemented on the FPGA 40. In other words, blocks 102and 104 may be performed prior a hardware implementation defined thekernel program (bitstream) 20 is implemented on the FPGA 40. Additionaldetails with regard to generating the heat map 30 will be describedbelow with reference to FIG. 5 .

At block 106, the processor 76 generates an updated power map. Forinstance, after the program (bitstream) 20 has been implemented by theFPGA 40, the processor 76 may receive data regarding operation of theFPGA 40 and refine or otherwise modify the power map 28 generated atblock 102. Similarly, at block 108, the processor 76 may generate anupdated heat map that may be based on the updated power map and the heatmap 30. The updated heat map may be modified version of the heat map 30generated at block 84, and the updated heat map may be generated basedon how the FPGA 40 operates after the kernel program (bitstream) 20 isimplemented.

At block 110, the processor 76 may control the FPGA 40 using the updatedpower map and the updated heat map. For instance, as described below,the processor 76 may receive data regarding operation of the FPGA 40.Utilizing the data and the updated power and heat maps, the processor 76may determine whether the power or temperature of a portion of the FPGA40 is undesirable (e.g., exceeds a threshold value), in which case theprocessor 76 may send commands to alter how the FPGA 40 is operating,among other actions.

Keeping the discussion of blocks 102 and 104 in mind, FIG. 5 is a flowchart of a process 120 for generating the power map 28 and a heat map 30of an integrated circuit such as the integrated circuit 12 or the FPGA40. The process 120 may be performed by the processor 32 by executingthe design software 14 stored on the memory 24. Additionally, theprocess 120 may be performed prior to implementing the kernel program(bitstream) 20 onto the FPGA 40. Furthermore, before proceeding, itshould be noted that details of the process 120 are explained below byreferencing FIGS. 6-10 .

At block 122, the processor 32 determines transceiver power of theintegrated circuit 12. Transceiver power includes expected powerconsumed by transceivers (e.g., transceiver banks) of the integratedcircuit 12. Referring now to FIG. 6 , which is a schematic diagram of aportion of an embodiment of the FPGA 40 (and the integrated circuit 12),the FPGA 40 includes sixteen transceiver banks 140. In otherembodiments, the FPGA 40 may include fewer or more transceiver banks140. Each of the transceiver banks 140 includes six channels 142 thatmay be used for communication between the FPGA 40 and other devices suchas the processor 76. In other embodiments of the FPGA 40, thetransceiver banks 140 may include fewer or more than six channels 142(e.g., one, two, three, four, five, seven, or more channels 142).Additionally, the channels 142 may allow for several communications tobe undertaken in various manners and/or components of the system 70. Forinstance, some of the channels 142 may be used for Ethernetcommunication, communication with the PCIe blocks 144, and/orcommunication with the processor 76.

In addition to the transceivers 140, the FPGA 40 includes fourPeripheral Component Interconnect Express (PCIe) blocks 144, which mayalso be utilized to allow the FPGA 40 to communicate with componentsthat may be included in the system 70, such as the processor 76 ormemory. While the illustrated embodiment of the FPGA 40 includes fourPCIe blocks 144, other embodiments of the FPGA 40 may include fewer ormore than four PCIe blocks 144 (e.g., one, two, three, five, or more).

The processor 32 may determine transceiver power by executing the designsoftware 14. For example, the design software 14 may include dataregarding various operations to be performed by the FPGA 40, thecollection of circuit components (e.g., logic elements) used by the FPGA40, a number of transceivers (e.g., transceiver blocks 140) that may beincluded in the FPGA 40, and the like. Based on a hardwareimplementation adopted by the FPGA 40 in accordance with the provideddesign, the processor 32 may determine which transceiver block 140 andPCIe blocks 144 will be implemented in the FPGA 40. The processor 32 maythen determine an expected amount of power to be consumed by thetransceiver blocks 140 and the PCIe blocks 144. For instance, powerconsumption values associated with the type of transceiver block 140 ormanner of communication (e.g., via Ethernet communication, PCIecommunication) used by transceiver blocks 140 may be specified by thedesign software 14, and the processor 32 may calculate the transceiverpower using these power consumption values and the corresponding numberof transceiver blocks 140, communication mediums, PCIe blocks 144, andthe like of the FPGA 40.

More specifically, the processor 32 may determine power consumptionvalues for each channel 142 of the transceiver blocks 140. For instance,based on a circuit design of the FPGA 40 provided to the design software14, the processor 32 may determine how many channels 142 of thetransceiver blocks 140 will be used for different types ofcommunication. Additionally, the processor 32 may determine thetransceiver power based on the number of channels 142 that will be usedfor each type of communication as well as the amount of power expectedto be consumed when a channel 142 is using a particular type ofcommunication. In other words, different amounts of power (e.g., varyingamounts of milliwatts) may be associated with different methods ofcommunication (e.g., via PCIe or Ethernet communication), and theprocessor 32 may determine an amount of power for each channel 142 basedon the type of communication to be used. The transceiver power may thenbe determined by summing all of the power consumption values associatedwith each channel 142.

Additionally, power consumption for each channel may be categorized intodigital and analog power. For instance, the processor 32 may generate atable that indicates digital power associated with the channels 142 oftransceiver bank 140A in column 146 and analog power associated with thechannels 142 in column 148. The digital and analog power consumptionassociated with each channel 142 of a respective transceiver bank 140may then be determined by summing entries from each of the columns 146and 148.

To further illustrate the transceiver power determination (i.e., thedetermination performed at block 122), FIG. 7 is provided. FIG. 7 is adiagram of a portion of an embodiment the FPGA 40 that shows powervalues (e.g., “252”, “253”, and “303”) associated with the channels 142of the transceiver blocks 140. As described above, the various powerconsumption values may be associated with a type of communication usedby a given channel. In the illustrated embodiment, the power values areassociated with Ethernet communication, PCIe communication, andcommunication via a processor interconnect, such as Intel® Ultra PathInterconnect (Intel® UPI). Channels 142 that do not include power values(e.g., channel 142B) correspond to channels 142 that are not expected tobe used. In any case, as discussed above, the processor 32 may determinepower consumed by a respective transceiver bank 140 by summing the powerconsumption values associated with the channels 142.

Returning to FIG. 5 , at block 124, the processor 32 may determine adefault static power associated with the integrated circuit 12 (e.g.,the FPGA 40). Static power may refer to an amount of power used by theportions of the FPGA 40 other than the partial reconfiguration regions74. For instance, static power includes power used by the transceiverblocks 140 and static region 72. However, because transceiver power maybe calculated at block 122, the processor 32 may not calculate orrecalculate power associated with the transceiver blocks 140 at block124. In other words, in some embodiments, at block 124, the processor 32may determine an amount of power associated with the static region 74but not the transceiver blocks 140.

In some embodiments, the static power may be determined as a function ofjunction temperature of the FPGA 40. For instance, FIG. 8 is a graph 160showing static power of the FPGA 40 as a function of junctiontemperature. Axis 162 includes junction temperature values (in degreesCelsius), and axis 164 includes power values (in watts) for the FPGA 40.The graph 160 includes data for two possible scenarios. Line 166 isrepresentative of an expected operation of the FPGA 40. In other words,the data reflected by the line 166 is indicative of a static power thatis expected to occur based on historical data, expected operations ofthe components of the FPGA 40, simulations of the operations of the FPGA40, and the like. On the other hand, line 168 is representative of anexpected static power consumed when the FPGA 40 is operating under amaximum power consumption condition, which may be specified by themanufacturer of the FPGA 40.

The data presented in the graph 160 may be provided to the designsoftware 14, and the processor 32 may determine the expected staticpower consumed by the FPGA 40 using such data. Additionally, based onthe static power determined for the entire FPGA 40, the processor 32 maydetermine an expected static power associated with each sector 48 of theFPGA 40. For instance, the static power associated with each sector 48at a given junction temperature may be determined by dividing the powervalue indicated by the graph 160 for that junction temperature by thenumber of sectors 48 of the FPGA 40. As such, the processor 32 maydetermine an expected amount of static power for the FPGA 40 as well asan expected amount of static power for each sector 49 of the FPGA 40.

Referring back to FIG. 5 , at block 126, the processor 32 may determinean amount of dynamic power associated with the static region 72 of theFPGA 40. Dynamic power may refer to an amount of power used when anintegrated circuit (e.g., integrated circuit 12, FPGA 40) is activelyoperating. For example, dynamic power of the FPGA 40 refers to powerconsumed by the FPGA 40 when the FPGA 40 is performing calculations. Thedynamic power associated with the static region 72 is the amount ofpower used by the static region 72 during dynamic operation of the FPGA40.

More specifically, the processor 32 may determine an amount of dynamicpower associated with the static region 72 based on the kernel program(bitstream) 20. For example, the processor 32 may determine a hardwareimplementation to be incorporated by the static region 72 and estimatean amount of power that such a hardware implementation would use whilethe FPGA 40 is dynamically operating (e.g., performing calculations).For instance, the kernel program (bitstream) 20 may include a netlist,which is a list of the electrical components of the FPGA 40 and thenodes to which the components are connected. For example, somecomponents (e.g., logic elements) of the FPGA 40 may receive power fromone or more voltage sources (e.g., power rails). As such, the processor32 may determine an estimated amount of dynamic power based on thecomponents of the FPGA 40 and the connections of the components. Forinstance, power may be determined using the following formula:P=CV ² Fα  (1)where P is power, C is capacitance, V is voltage, F is frequency, and ais an activity factor. The processor 32 may determine values for C, V,and F based on the kernel program (bitstream) 20. For example, thesevalues may be defined based on the circuit components or elements usedto implement the kernel program (bitstream) 20. The activity factor(i.e., a) is a multiplier that is used to take into account how activeor inactive the FPGA 40 is expected to be while operating. The processor32 may determine the value of a based on designer input. For example, auser may specify a value of a while designing the kernel program(bitstream) 20. In some embodiments, the value of a may be determinedbased on answers to questions presented to the designer. For example,questions regarding an expected usage of the FPGA 40 (e.g., whatcalculations the FPGA 40 will be used to execute) may be presented tothe designer while he or she is designing software (e.g., kernel program(bitstream) 20) of the FPGA 40.

The processor 32 may also estimate the dynamic power of each sector 48of the static region 72 in a similar manner as described above.Additionally, the power values for each sector 48 may be included in thepowers maps 28 generated by the processor 32. With this in mind, FIG. 9includes an embodiment of the power map 28 and a diagram of anembodiment of the FPGA 40. The illustrated power map 28 is a spreadsheetrepresentative of the sectors 48 of the FPGA 40. For example, cells ofcolumn 192 and 194 corresponds to transceiver blocks 140. Cells incolumns 196 and 197 as well as cells that are included in a group 198 ofcells correspond to the sectors 48 of the static region 72.

Referring back to FIG. 5 , at block 128, the processor 32 may determinedynamic power associated with the partial reconfiguration regions 74. Ingeneral, the processor 32 may determine the dynamic power of the partialreconfiguration regions 74 similarly to how the dynamic power of thestatic region 72 is determined at block 126. More specifically, theprocessor 32 may determine a number and position of partialreconfiguration regions 74 of the FPGA 40 based on the kernel program(bitstream) 20. For instance, FIG. 10 includes diagrams of severalembodiments of the FPGA 40. Each of the illustrated embodiments includesat least one partial reconfiguration region 74. While three examples areprovided in FIG. 10 , it should be noted that, in other embodiments, theFPGA 40 may include a different number of partial reconfigurationregions 74 (e.g., four or more), and the location of the partialreconfiguration regions 74 on the FPGA 40 may differ from theillustrated embodiments.

Additionally, based on the kernel program (bitstream) 20, the processor32 may determine an estimate for dynamic power of each sector 48 thepartial reconfiguration regions 74 of the FPGA 40. For example, asexplained above, the kernel program (bitstream) 20 may include anetlist. Based on the netlist, the processor 32 may determine power asdescribed above for the sectors 48 of the FPGA 40 that are included inthe partial reconfiguration regions 74. That is, using Formula 1, theprocessor 32 may determine an estimated amount of dynamic power based onthe components of the FPGA 40 and the connections of the components asdescribed by the netlist. It should be noted that the value for a usedin the calculation of the dynamic power of the partial reconfigurationregions 74 may differ from the value of a used in the calculation of thedynamic power of the static region 72.

For instance, FIG. 11 includes an example power map 28 and a diagram ofan embodiment of the FPGA 40 that includes two partial reconfigurationregions 74. The power map 28 of FIG. 11 includes a region 200 of cellsthat correspond to the sectors 48 of one of the partial reconfigurationregions 74 (e.g., AFU 1). In other words, amounts of power for variousportions of the power map 28 may be determined for each of the partialreconfiguration regions 74. Indeed, in some cases, the value of a ofFormula 1 may differ between different partial reconfiguration regions74.

It should be noted that each portion of the power map 28 thatcorresponds to a partial reconfiguration region 74 may be parameterizedby various metrics, such as frequency (i.e., ƒ) and the activity factor(i.e., α). Different partial reconfiguration regions 74 present incombination in the same device, or different partial reconfigurationregions 74 residing in the same area of a programmable logic device(e.g., FPGA 40) at different times may have different frequencies,different usage of resources, and different activity factors. The designsoftware 14 is aware of these differences such as differences in usageof resources and frequency. Moreover, the activity factor associatedwith a particular partial reconfiguration region 74 may be obtained fromuser input or empirical testing conducted with the particular partialreconfiguration region 74 in isolation.

In addition to dynamic power associated with each sector 48 of the FPGA40 (e.g., sectors 48 of the static region 72 or partial reconfigurationregions 74), the processor 32 may also determine power consumed by eachvoltage source to be utilized by the FPGA 40. For instance, the varioussectors 48 of the FPGA 40 may receive electric power via one or morepower rails. The processor 32 may determine power to be consumed fromeach of the power rails based on the netlist and the powerdeterminations described above. For example, the processor 32 maydetermine which sectors 48 are supplied with power from a particularvoltage rail, and the processor 32 may determine the power supplied bythe voltage rail by summing the power associated with those sectors 48.

Furthermore, the processor 32 may determine the total amount of powerconsumed by the FPGA 40. Such a determination may be made by summingpower consumption values. For instance, the total power consumed by theFPGA 40 may be determined by summing the power consumption values ofeach cell of the power map 28.

Furthermore, it should also be noted that the power map 28 may begenerated for a specific junction temperature of the FPGA 40 or theintegrated circuit 12. In other words, different power maps 190 may begenerated for different junction temperatures. For instance, the powermap 28 may correspond to power consumption values for one junctiontemperature, while other power maps may correspond to other junctiontemperatures.

Referring back to FIG. 5 , at block 130, the processor 32 may determineplatform data associated with system 70. Platform data includesinformation regarding a nature or type of integrated circuit 12 (e.g.,FPGA 40) and the processor 76 being used. For instance, the platformdata may include data regarding specific models of integrated circuits,processors, and hardware used in combination with the integrated circuit12, FPGA 40, or processor 76. The platform data may be obtained based onuser input from the designer during the design of the hardwareimplementation to be incorporated on the FPGA 40.

With respect to the integrated circuit 12, platform data may include atype of integrated circuit 12, a model of the integrated circuit 12, aswell as operating characteristics of the integrated circuit 12.Similarly, the platform data may also include the type of processor 76,a model of the processor 76, as well as operating characteristics of theprocessor 76. The platform data may also include other hardwareinformation regarding the system 70, such information regarding a heatsink to be used to cool the integrated circuit 12. For instance, theplatform data may include information regarding a model of a heat sinkas well as a type of thermal management provided by a heat sink (e.g., aheat sink with or without a fan or a heat sink that employs liquidcooling). Additionally, the platform data may include informationregarding an environment in which the system 70 will be operated. Forinstance, an expected ambient temperature of the environment in whichthe system 70 will be located when operating may be included in theplatform data. Moreover, the platform data may include an expectedairflow of the environment in which the system will be located whenoperating.

In some embodiments, the platform data may be obtained based on userinput. For instance, the design software 14 may include an interfacethat allows for the designer to input the model of the integratedcircuit 12, the processor 76, information regarding other hardware suchas a heat sink to be integrated with the integrated circuit 12, as wellas information regarding the environment in which the system 70 mayoperate, such as an expected ambient temperature. For instance, thedesign software 14 may provide drop-down boxes that allow for designerto select or otherwise provide information regarding the system 70.

Before continuing with the discussion of the process 120, it should benoted that the power map 28 may include ranges of power consumptionvalues. For instance, while one value may be given (e.g., as illustratedin FIG. 9 and FIG. 11 ), such a value may be the value that has a higherprobability of being the amount of consumed power as compared to otheramounts of consumed power. Multiple values may be used instead toprovide a range of power consumption values. The range may be used totake into account different potential values of a, whether performanceof the FPGA 40 is more likely to be associated with typical operation ora maximum power consumption condition, variations in environmentaltemperature or operation of a heat sink or cooling system associatedwith the FPGA 40, or a combination thereof.

Returning to FIG. 5 , at block 132, the processor 32 may determine anincidence coefficient matrix (ICM) based on the platform data. The ICMgenerally describes a relationship between power consumed by the FPGA 40and expected amounts of heat that is generated by the FPGA 40. The ICMtakes into account design details concerning the FPGA 40 (e.g.,transceiver blocks 140, static region 72, and partial reconfigurationregions 74) as well as the platform data (e.g., information regarding aheat sink used to cool the FPGA 40). The ICM may also be determinedbased on other information, such as transceiver power, default staticpower, static region dynamic power, and the like.

At block 134, the processor 32 may determine a heat factor. The heatfactor is a value or series of values that describes how efficiently orinefficiently the system 70 will be at removing heat from the FPGA 40.Additionally, the heat factor describes an amount of heat expected to begenerated by the consumption of electrical power of the FPGA 40. Inother words, the heat factor may provide an indication of the amount ofheat will be generated by FPGA 40 during operation. The processor 32 maydetermine the heat dissipation factor based on the platform data. Forexample, the measure of the amount of heat that may be generated by theFPGA 40 as well as an amount of heat that may be dissipated (e.g., by aheat sink) may be determined based on the FPGA 40 (e.g., a model of theFPGA 40, how the FPGA 40 has been programmed, physical components of theFPGA 40), other components associated with the FPGA 40, such as acooling system or heat sink, and the environment in which the FPGA 40will be located (e.g., expected ambient temperature).

At block 136, the processor 32 may generate the power map 28. Asdiscussed above, the power map 28 is indicative of the expected power tobe consumed by the FPGA 40. For example, the power map 28 may indicatean expected amount of power associated with each sector 48 of the FPGA40. The power map 28 can correspond to a particular junctiontemperature, and the processor 32 may generate several power maps 28,each of which pertain to a specific junction temperature value.Additionally, the power map 28 may be indicative of the power used byeach sector 48 of the FPGA 40 as well as each region, such as the staticregion 72 and the partial reconfiguration regions 74 (e.g., viasummation of power consumption values associated with sectors 48 thatare included in a particular region of the FPGA 40).

At block 138, the processor 32 may generate a heat map 30. The heat map30 may be generated based on the power map 28, platform data, the ICM,and the heat factor. In other words, for a particular hardwareconfiguration (e.g., a particular integrated circuit to be employed, thehardware implementation described by the kernel program (bitstream) 20,and a degree of cooling and/or heat dissipation to be provided (e.g., bya cooling system or heat sink)), the environment in which the integratedcircuit will be operated (e.g., expected ambient temperature), and howthe integrated circuit 12 (e.g., FPGA 40) will be used (e.g., asdescribed by activity factor α), and a relationship between power andtemperature (e.g., as described by the heat factor), the processor 32may generate the heat map 30.

With this in mind, FIG. 12 includes the power maps 28 and the heat maps30 that are associated with various scenarios. For example, each of theillustrated power maps 28 and heat maps 30 associated with variouspotential operating scenarios the FPGA 40 may encounter after thehardware implementation described by the kernel program (bitstream) 20is employed by the FPGA 40. As illustrated, the power maps 28 show wherea temperature sensor 210 may be located. Although the temperature sensor210 may be positioned in an area of the FPGA 40 that is associated withthe partial reconfiguration regions 74, in other embodiments, thetemperature sensor 210 may be positioned elsewhere on the FPGA 40.Moreover, in other embodiments, more than one temperature sensor 210 maybe used. The temperature sensor 210 may collect data of a temperaturearound the temperature sensor 210. Additionally, the temperature sensor210 may be communicatively coupled to the FPGA 40, the processor 76, orboth the FPGA 40 and the processor 76.

During operation of the system 70, the processor 76 may determine atemperature difference between a junction temperature of the FPGA 40 anda temperature detected by the temperature sensor 210. For example, asshown in FIG. 12 , each heat map 30 is associated with a value for“Delta T,” which is a difference between the temperature sensed by thetemperature sensor 210 and the junction temperature of the FPGA 40. Forexample, the heat map 30 may indicate a temperature associated with eachsector 48 of the FPGA 40. One sector 48 may be associated with onetemperature value according to the heat map 30, while the temperaturesensor 210 may measure another temperature value for the same sector 48.The “Delta T” reflects the difference between two such values.Additionally, it should be noted that before the kernel program(bitstream) 20 is implemented into the FPGA 40, the temperature valueused to determine the temperature difference (i.e., Delta T) may be apredicted value calculated by the processor 32.

As described above, a hardware implementation described by the kernelprogram (bitstream) 20 may be incorporated by the integrated circuit 12(e.g., the FPGA 40). The power maps 28 and heat maps 30 may be refinedafter incorporation of the hardware implementation. More specifically,and as described below, the processor 76 may update the power maps 28and heat maps 30 based on detected power values and by comparing thedetermined values to expected values used to generate the power maps 28and heat maps 30. In other words, while the power maps 28 and heat maps30 generated by the processor 32 may be estimates, data specific to theFPGA 40 may be obtained after implementation of the kernel program(bitstream) 20, and the processor 76 may update the power maps 28 andheat maps 30 based on the collected data.

With the foregoing in mind, FIG. 13 is a flow chart of a process 240 forrefining power maps 28 and heat maps 30. In brief, the processor 76 mayimplement a particular hardware into the FPGA 40 that includes a knownarrangement of circuit components that are programmed to perform certainoperations. As such, the processor 76 may have the value of the activityfactor, which may be a uniform value for each AFU. While operating theAFUs on the FPGA 40, the processor 76 may obtain power consumption andheat values to make boundary conditions for power and heat estimatesregarding the operations of the FPGA 40.

At a later time, the processor 76 may receive a design to incorporateanother hardware implementation for the FPGA 40. As such, the processor76 may update the estimates for portions of the power map 28 and theheat map 30 that correspond to the AFUs based on the previous power andheat measurements during the loading (e.g., about 50 milliseconds) ofthe hardware implementation. As the AFUs of the FPGA 40 perform theirrespective tasks, the processor 76 may take additional electrical andtemperature measurements and dynamically adjust the power map 28 and theheat map 30 to represent the current operations of the FPGA 40.

Referring now to the details of FIG. 13 , at block 242, a first kernelprogram (bitstream) 20 that may include a uniform correlation bitstreammay be loaded and implemented by the FPGA 40. It should be noted thatthe first kernel program 20 associated with block 242 may differ fromthe second kernel program 20 mentioned below. More specifically, thefirst kernel program 20 may describe a hardware implementation for thepartial reconfiguration regions 74 that differs from the hardwareimplementation described by the second kernel program 20 used to programthe FPGA 40 to perform certain desired operations by a designer. In oneembodiment, the first kernel program 20 may include a hardwareimplementation that is known. For instance, incorporation of thehardware implementation described by the first kernel program 20 mayresult in the CRAM of the partial reconfiguration regions 74 to beprogrammed to perform certain known operations. For example, the valueof the activity factor, a, may be known for each sector 48 of thepartial reconfiguration regions included in the first kernel program 20.As such, portions of power maps 28 and heat maps 30 associated with thehardware configuration of the first kernel program 20 may be generatedas a baseline or reference for the processor 76. With the first kernelprogram 20 implemented, as described below with respect to blocks 244,246, 248, and 250, the processor 76 may make several determinations(e.g., power consumption, current per rail, junction temperature) thatare specific to the FPGA 40. These determinations may be used to refineto the power maps 28 and heat maps 30.

At block 244, the processor 76 may measure current values for each railof the FPGA 40. That is, current values associated with voltage railsthat deliver power to the FPGA 40 may be measured. For instance, theFPGA 40 may be controlled by the processor 76, which may command theFPGA 40 to operate with certain operational characteristics. Forexample, the processor 76 may cause the partial reconfiguration regions74 to operate at a maximum output level. The processor 76 may detectcurrent values associated with power delivered via voltage rails to thevarious portions of the FPGA 40, such as the transceiver banks 140,static region 72, and partial reconfiguration regions 74. As describedbelow, the current measurements may be used to calculate measured powervalues, and the measured power values may be compared to expected powervalues.

At block 246, the processor 76 may measure junction temperature valuesof the FPGA 40 at various maximum operating frequencies based on thetemperature value received from the temperature sensor 210 and the heatmap 30. For example, the FPGA 40 may be operated in a manner representedby Scenario 2 of FIG. 12 in which each sector 48 of the partialreconfiguration regions 74 of the FPGA 40 is operated at a specificfrequency or maximum frequency. The junction temperature may bedetermined by the processor 76 by utilizing data from the temperaturesensor 210 as well as by referencing a heat map 28 associated with thekernel program 20 loaded onto the FPGA 40 at block 242. For example, ajunction temperature may be determined at frequency values of 100, 200,and 300 megahertz. In other embodiments, different frequency values maybe used, more frequency values may be used, and the difference betweentwo frequency values may differ. For instance, junction temperaturevalues may be measured at frequencies of 50, 100, 150, 200, 250, 300,and 350 megahertz.

Based on the determined junction temperature values, at block 248, theprocessor 76 may generate an equation defining junction temperature as afunction of frequency and the activity factor, a. For example, when theactivity factor has a constant value—which, as mentioned above, may bethe case when using the first kernel program—the junction temperaturevalues measured at various frequencies may be used to determine anequation for junction temperature based on frequencies.

At block 250, the processor 76 may determine parameters that allow formore accurate power and temperature determinations to be made. Morespecifically, the processor 76 may determine a T_(j)-max parameter. TheT_(j)-max parameter may be used to obtain a maximum junction temperaturefor different power values. The power values can be obtained based onfrequencies (e.g., there is a known amount of power or a range of powervalues associated with a particular frequency) in which certain sectors48 operate. So, for a given frequency, one may set a maximum error rangeof sorts for the calculated temperature values.

At block 252, the second kernel program (bitstream) 20 may be loadedonto the FPGA 40. In other words, the hardware implementation describedby the second kernel program (bitstream) 20 is incorporated onto theFPGA 40. Based on the power and temperature data gleaned from theoperation of the first kernel program 20, the power and temperatureproperties of the integrated circuit 12 during operation of other kernelprograms may be more accurately determinable. By way of example, theother kernel programs may include a second kernel program 20 that may bedeveloped by an end user of the FPGA 40.

At block 254, the power map 28 for the first kernel program 28 may beloaded (e.g., accessed) or generated by the processor 76. For example,the power map 28 may, as described above, be generated by the processor76. The power map 28 may also be stored on the memory 80 and accessibleby the processor 76. In other embodiments, the processor 76 may generatethe power map 28.

At block 256, the power map 28 may be refined (e.g., scaled) based onthe parameters generated at block 250 as well as measured values (e.g.,current measured at block 244). Regarding measured values, such ascurrent values, the processor 76 may determine an amount of powerutilized by a power rail. For example, electrical power with a knownvoltage (e.g., determined via a voltage regular or fully-integratedvoltage regulator) may have been used at block 244. With the knownvoltage and current values, the processor 76 may determine an amount ofpower for each power rail.

The processor 76 may modify the power map 28 based on a comparison ofthe determined amount of power and an expected amount of power. In otherwords, the processor 76 may modify previously generated power maps 28based on the chip-specific determinations made in blocks 244, 246, 248,and 250. More specifically, the known power values for a given powerrail may be compared to the values associated with the power map 28, andthe power map 28 may be refined based on such a comparison. Forinstance, when power values for a power rail differ from predictedvalues by a threshold amount (e.g., a percentage value or an amount ofpower), the power map 28 may be modified to reflect power values thatare more similar to those that were determined based on data obtainedfrom the FPGA 40. Moreover, to account for the possibility that morethan one AFU may be tracked at a given point in time, in some instances,such learning may be performed with an individual AFU in isolation(e.g., while the other AFUs disabled or not loaded (e.g., for thepurpose of isolating the power and/or activity factor of a specificAFU)). Such empirical calculations could also incorporate thestatistical distribution of power (e.g. min, max, mean, variance) orother factors such as power as a function of the input rate (i.e.,amount of data supplied to an AFU), operating mode of the AFU, or otherexogenous information. Such considerations may be incorporated into theestimation of power for an AFU at a given point in time, and couldincorporate probabilistic averaging when many AFUs are active on a givenintegrated circuit (e.g., FPGA 40).

At block 258, the processor 76 may refine the heat map 30 based on therefined power map 28. In other words, because the heat map 30 isgenerated based on the power map 30, changes to the power map 28 (e.g.,due to refinement) may cause the power map 30 to be altered.

It should be noted that the operations performed at blocks 254, 256, 258may be performed while the second kernel program (bitstream) 20 isloaded onto the FPGA 40. That is, during implementation of the secondkernel program (bitstream) 20, the previously generated power map 28 maybe refined. Additionally, the heat map 30 may be refined based on therefined power map 28.

The power maps 28 and heat maps 30 may continue to be refined duringoperation of the system 70. That is, as the FPGA operates 40, theprocessor 76 may make adjustments to the power maps 28 and heat maps 30.For instance, as part of the refinement, the processor 76 may determinea value for the activity factor α for each accelerator functional unitof the partial reconfiguration regions 74 based on electrical powerdata. Such a determination may be made after the second kernel program(bitstream) 20 has been loaded onto the FPGA 40 or after a portion ofthe second kernel program (bitstream) 20 has been loaded onto the FPGA40. For instance, a value for the activity factor α for a givenaccelerator functional unit may be determined when no other acceleratorfunctional units have been loaded onto the FPGA 40.

Continuing with the discussion of the process 240, at block 260, theprocessor 76 may determine the current for the power rails that supplypower to the partial reconfiguration regions 74. At block 262, theprocessor 76 may compare measured current values to expected currentvalues. For example, the processor 76 may determine expected currentvalues for a power rail based on the voltage of electrical power to bedelivered to a particular power rail. Alternatively, the processor 76may compare a measured power value, which can be determined based on ameasured current value and a known voltage values (e.g., a valueobtained from a voltage regulator for a power rail), to an expectedpower value.

At block 264, the processor 76 may refine the power map 28 based on thecomparison performed at block 262. For example, when the measured powerdiffers from an expected amount of power, the processor 76 may refinethe power maps 28. More specifically, because during operation of theFPGA 40, values of frequency, voltage, and capacitance are determinable,and thus, known, the processor 76 may determine that value of theactivity factor, a. The power maps 28 may be refined by the processor 76using the calculated activity factor in the determination of a newexpected power. That is, the processor 76 may modify the power maps 28to more closely reflect power values actually experienced by the FPGA40. Similarly, at block 266, the processor 76 may refine the heat maps30 based on the refined power maps 28. For instance, the updatedexpected power values may be used to determine temperature values.

Furthermore, the processor 76 may alter the performance of the FPGA 40based on data collected during operation of the system 70. Altering theperformance of the FPGA may include changing a frequency (e.g., clockspeed) of a partial reconfiguration 74, changing a data rate at whichinput is supplied to a partial reconfiguration 74, changing or limitingan availability of a partial reconfiguration 74 to peripherals such asmemory bandwidth, or another mechanism that may change an amount ofpower consumed by a partial reconfiguration 74. With this is mind, FIG.14 is a flow chart of a process 300 for controlling operation of theFPGA 40. The process 300 may be performed by the processor 76 or othersuitable processing circuitry.

At block 302, the processor 76 may receive data from and/or regardingthe FPGA 40. For example, the processor 76 may receive current valuesassociated with power rails, voltage values from a voltage regulator,and data associated with the FPGA 40, such as heat maps 28, power maps30, and information about the FPGA 40 (e.g., type of FPGA, hardwareimplementation as indicated by the kernel program (bitstream) 20).

At block 304, the processor 76 may determine power values andtemperature values associated with the FPGA 40. For example, theprocessor 76 may determine power values associated with each power railas well as each of the partial reconfiguration regions 74 of the FPGA.For example, each partial reconfiguration region 74 may be powered byone or more specific power rails, and the processor 76 may determine thepower associated with those rails. Similarly, based on power consumptionas well as detected temperature values from the heat sensor 210, theprocessor 76 may determine temperatures associated with portions of theFPGA (e.g., sectors 48 and/or partial reconfiguration regions 74) aswell as temperature differences between the temperatures reflected bythe temperature sensor 210 and predicted temperatures of the varioussectors 48 and/or regions (e.g., partial reconfiguration regions 74) ofthe FPGA 40.

At block 306, the processor 76 may determine whether a partialreconfiguration region 74 is consuming an amount of power that surpassesa threshold amount of power. For example, the threshold amount of powermay be an amount of power predicted by a power map 28 or a specificpercentage value above about the amount of power predicted by the powermap 28 (e.g., 10%, 20%, 25% or any other suitable percentage value).Additionally, or alternatively, the processor 76 may determine whether atemperature value associated with a portion of the FPGA 40 (e.g., asector 48 or partial reconfiguration region 74) exceeds a threshold.Similar to the power values, the threshold temperature may be atemperature difference between a predicted temperature (e.g., asindicated by the heat map 30) and a temperature indicated by thetemperature sensor 210 or determined according to the descriptionprovided above. When neither the power threshold not the temperaturethreshold is exceeded, the processor 76 may return to block 302 andreceive data regarding the FPGA 40.

However, when more than one partial reconfiguration region 74 exceeds athreshold, the processor 76 may proceed to block 308 and alter theoperation of one or more of the partial reconfiguration regions 74. Forexample, the processor 76 may alter operation of the partialreconfiguration region 74 that most exceeds a threshold, such that thepartial reconfiguration region 74 operates below the threshold.

The processor 76 may alter operation of a partial reconfiguration region74 in several ways. For example, the processor 76 may throttle aclocking frequency for the partial reconfiguration region 74. That is,the processor 76 may cause a frequency at which the partialreconfiguration region 74 is operating to decrease. Such a decreasewould cause the partial reconfiguration region 74 to use less power andgenerate less heat. As yet another example, the processor 76 may causethe partial reconfiguration region 74 to stop performing. That is, theprocessor may force the partial reconfiguration region 74 to refrainfrom performing an operation or cause the partial reconfiguration region74 to power down. Other examples of actions the processor changing adata rate at which input is supplied to the partial reconfiguration 74and changing or limiting an availability of the partial reconfiguration74 to peripherals such as memory bandwidth.

The techniques presented and claimed herein are referenced and appliedto material objects and concrete examples of a practical nature thatdemonstrably improve the present technical field and, as such, are notabstract, intangible or purely theoretical. Further, if any claimsappended to the end of this specification contain one or more elementsdesignated as “means for [perform]ing [a function] . . . ” or “step for[perform]ing [a function] . . . ”, it is intended that such elements areto be interpreted under 35 U.S.C. 112(f). However, for any claimscontaining elements designated in any other manner, it is intended thatsuch elements are not to be interpreted under 35 U.S.C. 112(f).

Example Embodiments of the Disclosure

The following numbered clauses define certain example embodiments of thepresent disclosure:

-   -   CLAUSE 1. A heat management system, comprising:    -   a programmable logic device (PLD); and        -   a first processor communicatively coupled to the PLD,            wherein the first processor is configured to:    -   determine a first set of power values for a first set of        portions of a plurality of portions of the PLD based on one or        more transceivers implemented via hardware on the PLD based on a        first design of the PLD;    -   determine a second set of power values for a second set of        portions of the plurality of portions based on a junction        temperature associated with the PLD;    -   determine a third set of power values for a third set of        portions of the plurality of portions configured to perform one        or more operations for the PLD, wherein the third set of power        values correspond to a set of expected power consumption values        when the third set of portions is performing the one or more        operations;    -   determine a temperature value for each portion of the plurality        of portions of the PLD based on the first set of power values,        second set of power values, the third set of power values, and        platform data associated with the PLD; and    -   generate a power map indicative of an expected power value for        each portion of the plurality of portions based on the first set        of power values, second set of power values, and the third set        of power values; and    -   generate a heat map indicative of an expected temperature value        for each portion of the plurality of portions.    -   CLAUSE 2. The heat management system of clause 1, wherein the        PLD comprises a field programmable gate array (FPGA).    -   CLAUSE 3. The heat management system of clause 1 or 2, wherein        the first processor is configured to determine:    -   a fourth set of power values for the second set of portions of        the plurality of portions based on an expected activity of one        or more hardware components in the second set of portions when        the one or more hardware components are performing an operation;        and    -   determine the temperature value for each portion of the        plurality of portions of the PLD based on the first set of power        values, second set of power values, the third set of power        values, the fourth set of power values, and the platform data        associated with the PLD.    -   CLAUSE 4. The heat management system of clause 1, 2, or 3,        wherein the platform data comprises information regarding a heat        sink, an expected airflow, or an expected ambient temperature.    -   CLAUSE 5. The heat management system of clause 1, 2, 3, or 4,        comprising a second processor configured to control a set of        operations of the PLD, wherein the second processor is        configured to control the set of operations in response to at        least one expected power value of the power map associated with        at least one portion of the plurality of portions exceeding at        least one respective power threshold value.    -   CLAUSE 6. The heat management system of clause 5, wherein the at        least one respective power threshold value corresponds to an        expected power consumption value associated with the respective        at least one portion of the plurality of portions during        operation of the PLD.    -   CLAUSE 7. The heat management system of clause 1, 2, 3, or 4,        comprising a second processor configured to control a set of        operations of the PLD, wherein the second processor is        configured to control the set of operations in response to at        least one the temperature value of the heat map associated with        at least one portion of the plurality of portions exceeding at        least one respective temperature threshold value.

CLAUSE 8. The heat management system of clause 1 or 2, wherein thetemperature value for each portion of the plurality of portions isdetermined at least partially based on a respective power valueassociated with a respective portion of the plurality of portions.

-   -   CLAUSE 9. The heat management system of clause 1 or 2, wherein        the third set of portions of the plurality of portions        corresponds to at least one partial reconfiguration region of        the PLD.    -   CLAUSE 10. A heat management system, comprising:    -   a field programmable gate array (FPGA) comprising configuration        memory, a plurality of transceiver blocks, and a plurality of        portions, wherein the plurality of portions comprises at least        one static region and at least one partial reconfiguration        region;    -   a temperature sensor configured to detect a temperature        associated with a portion of the plurality of portions; and    -   a first processor communicatively coupled to the FPGA, wherein        the processor is configured to:        -   receive a power map of the FPGA, wherein the power map is            indicative of a plurality of expected amounts of power of            the plurality of portions;        -   receive a heat map of the FPGA, wherein the heat map is            indicative of a plurality of expected temperature values of            the plurality of portions;        -   receive temperature data associated with the portion of the            plurality of portions from a temperature sensor during the            operation of the FPGA;        -   receive current data associated with one or more power rails            configured to couple to the FPGA, wherein the current data            represents one or more amounts of current present on the one            or more power rails during the operation of the FPGA;        -   refine the power map based on the current data; and        -   refine the heat map based on the current data.    -   CLAUSE 11. The heat management system of clause 10, wherein the        processor is configured to refine the power map based on a        difference between a current value associated with one of the        plurality of portions according to the power map and one of the        one or more amounts of current.    -   CLAUSE 12. The heat management system of clause 10 or 11,        wherein the processor is configured to:    -   receive one or more values associated with frequency and voltage        associated with the FPGA; and    -   refine the power map based on the current data and the one or        more values.    -   CLAUSE 13. The heat management system of clause 10, 11, or 12,        wherein the processor is configured to control a set of        operations of the FPGA in response to a difference between at        least one of the expected temperature values of the heat map        associated with at least one portion of the plurality of        portions and the temperature detected by the temperature sensor        exceeding a threshold.    -   CLAUSE 14. The heat management system of clause 10, 11, 12, or        13, wherein the heat map and the power map are generated by a        second processor separate from the first processor.    -   CLAUSE 15. A method for operating a field programmable gate        array (FPGA), the method comprising:    -   receiving, via a processor, a power map of a FPGA, wherein the        power map is indicative of a plurality of expected amounts of        power of a plurality of portions of the FPGA;    -   receiving, via the processor, a heat map of the FPGA, wherein        the heat map is generated based at least partially on the power        map, and wherein the heat map is indicative of a plurality of        expected temperature values of the plurality of portions;    -   receiving, via the processor, power data associated with one or        more power rails configured to couple to the FPGA, wherein the        power data represents one or more amounts of current present on        the one or more power rails during an operation of the FPGA; and    -   determining, via the processor, a plurality of amounts of power        of the plurality of portions of the FPGA based on the power        data;    -   determining, via the processor, whether at least one of the        plurality of amounts of power exceeds a respective power        threshold associated at least one portion of the plurality of        portions; and    -   altering, via the processor, at least one operation of the at        least one portion in response to the at least one of the amounts        of power exceeding the respective power threshold.    -   CLAUSE 16. The method of clause 15, wherein the respective power        threshold corresponds to a value greater than an expected amount        of power of the plurality of expected amounts of power.    -   CLAUSE 17. The method of clause 15 or 16, comprising:    -   receiving, via the processor, temperature data associated with a        portion of the plurality of portions from a temperature sensor        during the operation of the FPGA;    -   determining, via the processor, whether the temperature data        exceeds a respective temperature threshold associated with the        at least one portion; and    -   altering, via the processor, the at least one operation in        response to the temperature data exceeding the respective        temperature threshold.    -   CLAUSE 18. The method of clause 17, comprising:    -   determining, via the processor, a temperature associated with        the at least one portion based on the power data; and    -   determining whether the temperature data exceeds the respective        temperature threshold when the temperature associated with the        at least one portion exceeds the respective temperature        threshold.    -   CLAUSE 19. The method of clause 15 or 16, wherein the processor        is configured to alter operation of the at least one portion by        stopping the operation of the at least one portion.    -   CLAUSE 20. The method of clause 15 or 16, wherein the processor        is configured to alter operation of the at least one portion by        reducing an operating frequency of the at least one portion.    -   CLAUSE 21. A non-transitory, computer-readable medium comprising        instructions that, when executed by one or more processors,        cause the one or more processors to:    -   determine a plurality of power values for a plurality of        portions of the PLD based on a design of the PLD, a junction        temperature associated with the PLD, and an expected amount of        power consumption associated with the PLD;    -   generate a temperature value for each portion of the plurality        of portions of the PLD based on the plurality of power values        and platform data associated with the PLD;    -   generate a power map indicative of an expected power value for        each portion of the plurality of portions based on the plurality        of power values; and    -   generate a heat map indicative of an expected temperature value        of each portion of the plurality of portions.    -   CLAUSE 22. The non-transitory, computer-readable medium of        clause 21, wherein the instructions are configured to cause the        one or more processors to:    -   receive temperature data associated with a first portion of the        plurality of portions from a temperature sensor during the        operation of the PLD;    -   receive current data associated with one or more power rails        configured to couple to the PLD, wherein the current data        represents one or more amounts of current present on the one or        more power rails during the operation of the PLD;    -   refine the power map based on the current data; and    -   refine the heat map based on the current data.    -   CLAUSE 23. The non-transitory, computer-readable medium of        clause 22, wherein the instructions are configured to cause the        one or more processors to alter an operation of the PLD based on        the heat map.    -   CLAUSE 24. The non-transitory, computer-readable medium of        clause 21, 22, or 23, wherein the plurality of power values        comprises a first set of power values associated with a first        portion of the plurality of portions, wherein the first portion        corresponds to a partial reconfiguration region.    -   CLAUSE 25. The non-transitory, computer-readable medium of        clause 21, 22, 23, or 24, wherein the PLD comprises a field        programmable gate array (FPGA).

What is claimed is:
 1. A system, comprising: a first integrated circuitdevice comprising a plurality of portions; and a second integratedcircuit device communicatively coupled to the first integrated circuitdevice, wherein while the first integrated circuit device is operating,the second integrated circuit device is configurable to: access a heatmap indicative of a plurality of expected temperature values of theplurality of portions; receive temperature data associated with aportion of the plurality of portions; determine, based on thetemperature data, whether a temperature threshold associated with atleast one portion of the plurality of portions has been exceeded; andalter at least one operation of the at least one portion in response tothe temperature threshold being exceeded.
 2. The system of claim 1,wherein the first integrated circuit device comprises a programmablelogic device.
 3. The system of claim 2, wherein the programmable logicdevice comprises a field-programmable gate array (FPGA).
 4. The systemof claim 3, wherein the plurality of portions comprises a static regionof the FPGA.
 5. The system of claim 3, wherein the plurality of portionscomprises a partial reconfiguration region of the FPGA.
 6. The system ofclaim 2, wherein the second integrated circuit device comprises aprocessor.
 7. The system of claim 1, comprising a temperature sensorconfigurable to generate the temperature data.
 8. The system of claim 1,wherein while the first integrated circuit device is operating, thesecond integrated circuit device is configurable to: access a power mapof the first integrated circuit device, wherein the power map isindicative of a plurality of expected amounts of power of the pluralityof portions; receive power data associated with one or more power railsconfigured to couple to the first integrated circuit device, wherein thepower data comprises one or more amounts of current measured on the oneor more power rails during operation of the first integrated circuitdevice; determine a plurality of amounts of power of the plurality ofportions based on the power data; determine whether at least one of theplurality of amounts of power exceeds a power threshold associated withthe at least one portion of the plurality of portions; and alter the atleast one operation of the at least one portion in response to the atleast one of the plurality of amounts of power exceeding the powerthreshold.
 9. The system of claim 1, wherein the second integratedcircuit device is configurable to alter the at least one operation ofthe at least one portion by: stopping the at least one operation of theat least one portion; or reducing an operating frequency of the at leastone portion.
 10. A tangible, non-transitory computer-readable mediumcomprising instructions that, when executed by a first integratedcircuit device, cause the first integrated circuit device to: access aheat map of a second integrated circuit device configurable to becommunicatively coupled to the first integrated circuit device, whereinthe heat map is indicative of a plurality of expected temperature valuesof a plurality of portions of the second integrated circuit device; andwhile the second integrated circuit device is operating: receivetemperature data associated with a portion of the plurality of portions;determine, based on the temperature data, whether a temperaturethreshold associated with at least one portion of the plurality ofportions has been exceeded; and alter at least one operation of the atleast one portion in response to the temperature threshold beingexceeded.
 11. The tangible, non-transitory computer-readable medium ofclaim 10, wherein the second integrated circuit device comprises aprogrammable logic device.
 12. The tangible, non-transitorycomputer-readable medium of claim 11, wherein the plurality of portionscomprises at least one static region, at least one partialreconfiguration region, or both.
 13. The tangible, non-transitorycomputer-readable medium of claim 10, wherein the instructions, whenexecuted, cause the first integrated circuit device to: access a powermap of the second integrated circuit device, wherein the power map isindicative of a plurality of expected amounts of power of the pluralityof portions; and while the second integrated circuit device isoperating: receive power data associated with one or more power railsconfigured to couple to the second integrated circuit device, whereinthe power data comprises one or more amounts of current measured on theone or more power rails during operation of the second integratedcircuit device; determine a plurality of amounts of power of theplurality of portions based on the power data; determine whether atleast one of the plurality of amounts of power exceeds a power thresholdassociated with the at least one portion of the plurality of portions;and alter the at least one operation of the at least one portion inresponse to the at least one of the plurality of amounts of powerexceeding the power threshold.
 14. The tangible, non-transitorycomputer-readable medium of claim 13, wherein the instructions, whenexecuted, cause the first integrated circuit device to: determine atemperature associated with the at least one portion based on the powerdata; and determine whether the temperature threshold has been exceededwhen the temperature associated with the at least one portion exceedsthe temperature threshold.
 15. The tangible, non-transitorycomputer-readable medium of claim 13, wherein the instructions, whenexecuted, cause the first integrated circuit device to refine the powermap based on the power data to generate a refined power map.
 16. Thetangible, non-transitory computer-readable medium of claim 15, refinethe heat map based on the refined power map.
 17. A system, comprising: afirst integrated circuit device comprising a plurality of portions;memory comprising a heat map indicative of a plurality of expectedtemperature values of the plurality of portions; and a second integratedcircuit device communicatively coupled to the first integrated circuitdevice and the memory, wherein while the first integrated circuit deviceis operating, the second integrated circuit device is configurable to:access the heat map; receive temperature data associated with a portionof the plurality of portions; determine, based on the temperature data,whether a temperature threshold associated with at least one portion ofthe plurality of portions has been exceeded; and alter at least oneoperation of the at least one portion in response to the temperaturethreshold being exceeded.
 18. The system of claim 17, wherein while thefirst integrated circuit device is operating, the second integratedcircuit device is configurable to: access a power map of the firstintegrated circuit device, wherein the power map is indicative of aplurality of expected amounts of power of the plurality of portions;receive power data associated with one or more power rails configured tocouple to the first integrated circuit device, wherein the power datacomprises one or more amounts of current measured on the one or morepower rails during operation of the first integrated circuit device;determine a plurality of amounts of power of the plurality of portionsbased on the power data; determine whether at least one of the pluralityof amounts of power exceeds a power threshold associated with the atleast one portion of the plurality of portions; and alter the at leastone operation of the at least one portion in response to the at leastone of the plurality of amounts of power exceeding the power threshold.19. The system of claim 17, wherein the plurality of portions comprisesa static region of the first integrated circuit device, a partialreconfiguration of the first integrated circuit device, or both.
 20. Thesystem of claim 17, wherein the second integrated circuit device isconfigurable to alter the at least one operation of the at least oneportion by: stopping the at least one operation of the at least oneportion; or reducing an operating frequency of the at least one portion.